Make concrete message_passing implementation public#130
Make concrete message_passing implementation public#130NEOatNHNG wants to merge 1 commit intoeclipse-score:mainfrom
Conversation
The alias alone is not usable from other modules.
NEOatNHNG
requested review from
LittleHuba,
castler and
hoe-jo
as code owners
LittleHuba
added
the
import-started-do-not-modify
|
Closing this, as visibility was extended appropriately for other S-CORE modules to access the concrete targets. |
|
We have other use cases in infrastructure components apart from logging where we would like to re-use the message passing. I mean it is OK if we don't want S-CORE applications to use message passing directly, but other infrastructure components should be fine. Similar argument could be made for shared_memory from baselibs. We also don't want applications to use that directly but we don't limit the visibility there either. Most current example is the someip gateway where @lurtz is working on a bridge implementation which would also need to access message_passing. But we have also ETAS-internal use cases for this. @mishraajitesh |
LittleHuba
removed
the
import-started-do-not-modify
|
@NEOatNHNG could you please give some insight into the ETAS-internal use cases? |
2 participants
The alias alone is not usable from other modules.